MSAG to RCL Synchronization

The MSAG to RCL Road Centerline Synchronization quality control (QC Quality Control) check identifies Master Street Address Guide (MSAG) records that do not correspond to a road segment in the road centerlines (RCL) layer.

Note: Synchronization QC checks can have leading zeros in the Emergency Service Number (ESN Emergency Service Number. A three to five digit number representing a unique combination of emergency service agencies (law enforcement, fire and emergency medical service) designated to serve a specific range of addresses within a particular geographical area, or Emergency Service Zone (ESZ). The ESN facilitates selective routing and selective transfer, if required, to the appropriate PSAP and dispatching of the proper service agency(ies).) fields for any of the layers or tables used in the QC check. The leading zeros will not negatively affect the comparison and an accurate fallout for the synchronization check is created, including accurately displaying your data with any leading zeros.

To run this check, the following is required.

  • MSAG table

  • Road centerline feature class with road name, address range, and zone information

Configurations for QC check parameters contain filters to prevent selecting incompatible field types.

The following parameters can be specifically configured for the MSAG to RCL Synchronization QC check.

  • Run On: Non-configurable. This QC check inspects the target dataset.

  • Severity: Sets the importance level of this QC check’s fallouts. Critical fallouts prevent export package outputs but will still provide fallouts.

  • MSAG Name: The name of the MSAG table.

  • MSAG - Reporting Unique ID: A unique identifier in the MSAG table that can be used to uniquely identify a singular feature.

  • MSAG - Address Number Prefix: Represents the address number prefix on the MSAG record.

  • MSAG - Low Range: Represents the MSAG record's low range.

  • MSAG - High Range: Represents the MSAG record's high range.

  • MSAG - Street Full Name: A list of street name fields that form the entire street name. For example: LSt_PreDir, LSt_Name, LSt_Typ, LSt_PosDir.

  • MSAG - Odd/Even/Both (OEB): Indicates whether the MSAG record contains odd, even, or both range values.

  • MSAG - Emergency Service Number (ESN): Represents the MSAG record's Emergency Service Number (ESN).

  • MSAG - MSAG Community: Represents the MSAG record's MSAG Community.

  • Road Centerline (RCL) Name: The name of the road centerline layer.

  • RCL - Unique ID: A unique identifier in the Roads layer that can be used to uniquely identify a singular feature.

  • RCL - Left Address Number Prefix: Represents the address number prefix on the left side of the road segment.

  • RCL - Right Address Number Prefix: Represents the address number prefix on the right side of the road segment.

  • RCL - Left FROM Address: Represents the address number on the FROM node on the left side of the road segment.

  • RCL - Left TO Address: Represents the address number on the TO node on the left side of the road segment.

  • RCL - Right FROM Address: Represents the address number on the FROM node on the right side of the road segment.

  • RCL - Right TO Address: Represents the address number on the TO node on the right side of the road segment.

  • RCL - Parity Left: Indicates whether the left side of the road segment contains odd, even, both or zero address range values.

  • RCL - Parity Right: Indicates whether the right side of the road segment contains odd, even, both or zero address range values.

  • RCL - Street Full Name: A list of street name fields that form the entire street name. For example: LSt_PreDir, LSt_Name, LSt_Typ, LSt_PosDir.

  • RCL - ESN Left: Represents the Emergency Service Number (ESN) on the left side of the road segment.

  • RCL - ESN Right: Represents the Emergency Service Number (ESN) on the right side of the road segment.

  • RCL - MSAG Community Name Left: Represent the MSAG Community Name on the left side of the road segment.

  • RCL - MSAG Community Name Right: Represent the MSAG Community Name on the right side of the road segment.

  • Case Sensitivity: Select Match Case to enable and maintain the integrity of upper or lower case text in your data. See Case Sensitivity.

The following information is included for this QC check's fallout output.

  • QC check name
  • Description of the QC check
  • Unique identifier of the MSAG record not matching road centerlines
  • Low and high range of the MSAG record not matching road centerlines
  • Street name of MSAG record not matching road centerlines

  • Specific failure information – criteria causing MSAG to RCL comparison record to fail. The fallout message values are added to the Extended Information description field in the fallout report. The message identifies specific fallout messaging values to assist in the identification of mismatching fields for the MSAG records and road centerline features. These features display up to the first 5 values listed in alphanumeric order. This list exists for the following features.

    • RCL's AdNumPre
    • RCL's Unique ID
    • MSAG's ESN
    • MSAG's MSAG Community

There are many examples when completing MSAG to RCL Synchronization QC checks. Below are some examples.

The MSAG record’s low and/or high range value conflict with the MSAG’s listed parity values. In this example, Venice Blvd has a parity value that does not match correctly against the MSAG’s low and high ranges. The MSAG record must be corrected before further analysis can be conducted.

Here is an image of an example when a MSAG record's low and high range value do not match the parity.

Here is an image of an example when a MSAG record's low and high range value do not match the parity.

The MSAG record’s low range value is larger than the record’s high range value. In this example, Washington Blvd’s low range of 2000 is larger than its high range of 1098. The MSAG record must be corrected before further analysis can be conducted.

Here is an image of an example when a MSAG record's low range is greater than the high range.

Here is an image of an example when a MSAG record's low range is greater than the high range.

The MSAG record matches multiple road segments with the same street full name and address ranges. In this example, there are at least two La Cienega Blvd’s that cover the 4001-4207 address range with the same ESN and MSAG Community.

Here is an image of an example when a MSAG record can be placed on multiple road segments.

Here is an image of an example when a MSAG record can be placed on multiple road segments.

 

The MSAG record matches both sides of the same road segment with the same street full name and address ranges. In this example, E Santa Monica St’s matching road segment covers the 751-799 address range on both sides of the road. The road contains the correct ESN and MSAG Community values but needs to be updated so only one side reflects the MSAG record's address range values.

Here is an image of an example when an MSAG record can be placed multiple times on a single road segment.

Here is an image of an example when an MSAG record can be placed multiple times on a single road segment.

 

The MSAG record’s full street name does not exist in the in the road centerline (RCL) layer. In this example, Quincy St is not present in the RCL layer.

Here is an image of an example when a MSAG record has no matching RCL street name.

Here is an image of an example when a MSAG record has no matching RCL street name.

 

The MSAG record’s full street name only matches road centerlines that have a blank or 0-0 address range. In this example, Adams Dr exists in the RCL layer only as a road with zero or blank address ranges.

Here is an image of an example when a MSAG record only corresponds to road segments with zero / missing ranges.

Here is an image of an example when a MSAG record only corresponds to road segments with zero / missing ranges.

 

The MSAG record only matches road centerlines with the same street full name, but different MSAG Community and ESN values. In this example, Culver Dr exists in the RCL layer, but the roads contain the wrong MSAG Community and ESN values as compared to the MSAG record. Typically, the road attributes are updated to ensure accuracy.

Here is an image of an example when a MSAG record only corresponds to a road segment with a different MSAG Community and ESN.

Here is an image of an example when a MSAG record only corresponds to a road segment with a different MSAG community and ESN.

 

The MSAG record only matches road centerlines with the same street full name, but different ESN values. In this example, Crenshaw Blvd SW exists in the RCL layer, but roads contain the wrong ESN values as compared to the MSAG record. Typically, the road attributes are updated to ensure accuracy.

Here is an image of an example when a MSAG record only corresponds to a road segment with a different ESN.

Here is an image of an example when a MSAG record only corresponds to a road segment with a different ESN.

 

The MSAG record only matches road centerlines with the same street full name, but different MSAG Community values. In this example, Adams Blvd exists in the RCL layer, but the roads contain the wrong MSAG Community values as compared to the MSAG record. Typically, the road attributes are updated to ensure accuracy.

Here is an image of an example when a MSAG record only corresponds to a road segment with a different community.

Here is an image of an example when a MSAG record only corresponds to a road segment with a different community.

 

The MSAG record matches a road centerline’s street full name, ESN, MSAG Community and address ranges but fails to match its address number prefix, causing the mismatch. In this example, La Brea Blvd exists in the road centerline and matches every value in the MSAG record except for the address number prefix value.

Here is an image of an example when a MSAG record's adnumpre value does not match road segment.

Here is an image of an example when a MSAG record's adnumpre value does not match road segment.

 

The MSAG record matches a road centerline’s street full name, ESN, and MSAG Community, but the MSAG’s address range is not entirely covered by the road’s address range. In this example, NE Jefferson Blvd exists in the RCL layer but its range of 401-449 does not entirely cover the MSAG record.

Here is an image of an example when a MSAG record falls in a gap within the corresponding road ranges.

Here is an image of an example when a MSAG record falls in a gap within the corresponding road ranges.